home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-17
/
niscangs.zip
/
SAPI.DOC
< prev
next >
Wrap
Text File
|
1991-10-31
|
4KB
|
115 lines
SAPI scanner driver
SAPI.EXE
November 1, 1991
The SAPI scanner driver is a revision 6 scanner driver (see REV6.DOC for
more information) providing Black and White, Gray Scale and COlor scanning for
the current ZSoft products.
The ZSoft SAPI scanner driver requires the presents of a manufacturer
supplied scanner driver (referred to in this document as SAPI.SYS since the
actual name varies from manufacturer to manufacturer. Logitech's SAPI
driver is called HHSCAND.SYS). SAPI.SYS should be loaded before the ZSoft
driver.
SAPI.EXE also REQUIRES that the scanner hardware be setup for interrupts.
This has NOT been the case for previous ZSoft scanner drivers.
The commands provided by the SAPI scanner driver are listed below in the
example of the /H parameter.
ZSoft Scanner Driver, version 6.00
Copyright (C) ZSoft Corp. 1991. All rights reserved.
Valid commands:
/Bxxx = interrupt Buffer size in K (default is 8k)
/Cx = application Code (1-4)
/H = display this Help text
/? = display this help text
/Tx = do diagnostic Testing (verify communication with scanner)
/V = Verbose messages and status displays
/U = Unload driver
/B
==
The interrupt buffer will hold the scan data until the application is able
to retrieve the data from the scanner driver. If the application can not
request the data fast enough or often enough then "drop outs" or "hits" can
occur in the scanned picture. Increasing the buffer size allots the
application more time to process the scan data before it must retrieve
additional data from the scanner driver. The idea here is to use as small
an interrupt buffer as you can without getting any "drop outs" in your
pictures.
/C
==
In order to maximize the scanner functionality available to the application,
the /C parameter is used. This command parameter is usually set by the
install program. If the parameter is omitted, the application will still
work, but may be missing some features. The codes are:
/C1 = Paintbrush Plus (DOS)
/C2 = Paintbrush Plus (WIN)
/C3 = Paintbrush 4 Plus (DOS)
/C4 = Publisher's Paintbrush (Win)
Manufacturer Notes
==================
At this time only the Logitech ScanMan and ScanMan 256 have been tested
with the SAPI.EXE scanner driver. Any Black and White or Grayscale scanner
should work with this driver, however, no color support exists at this
time. Do to the lack of software control over the Logitech scanners the
SAPI driver can sometimes return invalid data for a scan. In order to
avoid this problem be sure that the switch settings on the hand scanner are
set to match the selections made in the application. For the ScanMan 256
be sure that the mode switch is set to 256 BEFORE SAPI.EXE is loaded or
grayscale may not be available as an option within the application.
SAPI Messages
=============
'Supporting: ???????????'
This message is displayed upon successful initialization of the SAPI
scanner. The name and model of the scanner found will be displayed.
SAPI Error Messages
===================
'Manufacturer driver not found! SAPI NOT loaded.'
This message is displayed when the scanner driver can not find the "helper"
driver (provided by the scanner maufacturer). The ZSoft SAPI scanner
driver requires that this driver be loaded before we can load.
'Scanner not responding (do you have the right address?)'
This message is displayed at initialization time if the scanner driver cannot
successfully communicate with the scanner.
'Error communicating with manufacturers driver (????)'
This message is displayed when an error occurs while sending or receiving
information from the manufacturer supplied driver. An error code is
included in the message to help identify the problem.
'Scanner hardware not configured for interrupts!'
The SAPI.EXE driver requires interrupts to function. The scanner
hardware interface must be configured to use interrupts. With most
manufacturers drivers the interrupt can be set with a command line
parameter to the driver (e.g. /I=7, sets interrupt 7).